-
Notifications
You must be signed in to change notification settings - Fork 182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add browser events and describe their payload #838
Conversation
Also, removing exception event; will be adding it as separate generic event.
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
as it's moved to a separate PR
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
Closed as inactive. Feel free to reopen if this PR is still being worked on. |
@open-telemetry/specs-semconv-approvers can someone please re-open this PR? thanks. |
@scheler please resolve conflicts for this one, thank you |
as discussed in Event SIG on 7/26, since it is added after the event is emitted by the instrumentation. Keeping session.id since it's well agreed upon.
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
Closed as inactive. Feel free to reopen if this PR is still being worked on. |
Add browser events and describe their payload
Changes
This PR adds the semantic conventions for browser events describing their name and payload. This is based on the recently agreed upon convention that payload will go in LogRecord's body field, and that the payload fields in the body do not need to be part of global registry and therefore do not need to have a namespace.
NOTE: not adding the yaml version since that's not ready yet from the build-tools perspective.
Merge requirement checklist
[chore]